6 Upgrading and Redeploying ADP and JVMD

Upgrading JVMD Engine

This section describes the methods to upgrade JVMD Engine. It consists of the following:

• Upgrading JVMD Engine Using Application Performance Management Page

• Upgrading JVMD Engine Manually Using ApmEngineSetup.pl

Redeploying JVMD Engine

To redeploy JVMD Engine deployed on a Managed Server, follow these steps:

1. From the Setup menu, select Middleware Management, then select Application Performance Management.

2. If you want to redeploy a single JVMD Engine, on the Application Performance Management page, select the JVMD Engine you want to redeploy, then click Redeploy.

   If you want to redeploy more than one JVMD Engine, on the Application Performance Management page, select the JVM Diagnostics Engines node, then click Redeploy.

3. On the Redeploy JVMD Engines page, select the JVMD Engines you want to redeploy.

4. For each JVMD Engine you have chosen to redeploy, specify a value for Host Credentials. These credentials are the host credentials of the host on which the JVMD Engine you selected is deployed. Click Apply.

5. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

6. Click Redeploy.

Upgrading ADP Engine

This section describes the methods to upgrade JVMD Engine. It consists of the following:

• Upgrading ADP Engine Using Application Performance Management Page

• Upgrading ADP Engine Manually Using ApmEngineSetup.pl

Redeploying ADP Engine

To redeploy ADP Engine deployed on a Managed Server, follow these steps:

1. From the Setup menu, select Middleware Management, then select Application Performance Management.

2. If you want to redeploy a single ADP Engine, on the Application Performance Management page, select the ADP Engine you want to redeploy, then click Redeploy.

   If you want to redeploy more than one ADP Engine, on the Application Performance Management page, select the ADP Engines node, then click Redeploy.

3. On the Redeploy ADP Engines page, select the ADP Engines you want to redeploy.

4. For each ADP Engine you have chosen to redeploy, specify a value for Host Credentials. These credentials are the host credentials of the host on which the ADP Engine you selected is deployed. Click Apply.

5. Specify a value for Admin WebLogic Credentials. These credentials are the credentials for the Administration Server of the Enterprise Manager WebLogic domain.

6. Click Redeploy.

Upgrading or Redeploying JVMD and ADP Agents Using Application Performance Management Page

To upgrade or redeploy JVMD and ADP Agents on monitored WebLogic domains using the Application Performance Management page, follow these steps:

1. From the Setup menu, select Middleware Management, then select Application Performance Management.

2. On the Application Performance Management page, under the Application Performance Management Agents section, click Manage Diagnostics Agents.

   Note:

   If no active JVMD or ADP Engines are present, and no JVMD or ADP Agents are deployed, the Manage Diagnostics Agents button is disabled.

3. For Operation, select Upgrade.

   Note:

   Alternatively, to reach this point, you can click the upgrade icon displayed beside ADP Agents Count or JVMD Agents Count, on the Application Performance Management page. Note that this icon is displayed only if a software version different from the current version of the ADP or JVMD Agent software is available.

   If you select Expand All from the View menu, you can view the target name, target type, target host, target status, platform, and so on of all the discovered WebLogic Administration Servers and Managed Servers (part of all discovered WebLogic domains).

   Select the JVMD and ADP Agents you want to upgrade or redeploy. Click Next.

4. On the Target Credentials page, for each WebLogic domain, specify a value for Oracle WebLogic Administration Server Host Credentials and Oracle WebLogic Domain Credentials, then click Apply.

   Oracle WebLogic Administration Server Host Credentials are the host credentials for the host on which the Management Agent that is monitoring the selected WebLogic domain is running. Oracle WebLogic Domain Credentials are the credentials for the Administration Server of the selected WebLogic domain.

   Click Next.

5. On the ADP Agents Configurations page, for each WebLogic domain, select an ADP Engine for Available ADP Engines, then click Apply. All the ADP Agents deployed on the Managed Servers of the selected WebLogic domain will report to the selected ADP Engine.

   You can specify an alternate location for the ADP Agent software, which is used if the specified Administration Server Host Credentials do not have write permissions on the default location. To do this, under the Agent Directory section, select Edit the default ADP Agent Directory location if required, then specify a value for Agent Directory.

   If the WebLogic Home and Middleware Home fields are displayed under the Additional Configuration section, specify values for them. The WebLogic Home and Middleware Home fields are displayed if their values could not be obtained internally.

   Also, sometimes when the WebLogic Administration Server is behind a firewall or on a virtual host, the application may not be able to connect to it, using the default host value. In this case, you may need to provide some additional information in the Additional Configuration section. For example, if the WebLogic Administration Server is on a virtual host, and the application cannot connect to it using the default host value, you may have to provide the virtual host IP address in the Additional Configuration section.

   Click Next.

6. On the JVMD Agents Configurations page, for each WebLogic domain, select a JVMD Engine for Available JVMD Engines, then click Apply. All the JVMD Agents deployed on Managed Servers of the selected WebLogic domain will report to this JVMD Engine. Alternatively, you can select Other to connect to a load balancer in case of multiple engines.

   If the WebLogic Home and Middleware Home fields are displayed under the Additional Configuration section, specify values for them. The WebLogic Home and Middleware Home fields are displayed if their values could not be obtained internally.

   Also, sometimes when the WebLogic Administration Server is behind a firewall or on a virtual host, the application may not be able to connect to it, using the default host value. In this case, you may need to provide some additional information in the Additional Configuration section. For example, if the WebLogic Administration Server is on a virtual host, and the application cannot connect to it using the default host value, you may have to provide the virtual host IP address in the Additional Configuration section.

   Click Next.

7. On the Enterprise Manager OMS Credentials page, specify a value for Oracle Enterprise Manager WebLogic Administration Server Host Credentials, and Oracle Enterprise Manager WebLogic Domain Credentials.

   Note:

   The Enterprise Manager OMS Credentials page is displayed when you click Next on the JVMD Agents Configurations page, only if you have chosen to redeploy or upgrade at least one ADP Agent. OMS credentials are not required to redeploy or upgrade JVMD Agents.

   Oracle Enterprise Manager WebLogic Administration Server Host Credentials are the host credentials of the OMS host. The Oracle Enterprise Manager WebLogic Domain Credentials are the domain credentials of the Enterprise Manager WebLogic domain.

   Click Next.

8. On the Review page, review all the information, then click Upgrade.

   When you click Upgrade, the Diagnostic Agents Deployment Status page appears, which you can use to monitor the progress of the submitted job.

Upgrading JVMD Agents Manually Using deploy_jvmdagent.pl

You can upgrade JVMD Agents manually, using the deploy_jvmdagent.pl script. You can run this script only in silent mode, that is, you must specify all the input details using a properties file.

To upgrade JVMD Agents manually using deploy_jvmdagent.pl, follow these steps:

1. Navigate to the following location on the OMS host:

   $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.4.0/archives/jvmd/deployment_Scripts/agent/jvmd/

2. View the README.txt file, for information on using the deploy_jvmdagent.pl script.

3. Specify all the inputs in a properties file, then use the following command:

   perl deploy_jvmdagent.pl <properties_file_name>

   If you do not pass the name of the properties file as a parameter while running deploy_jvmdagent.pl, deploy_jvmdagent.pl looks for a properties file named jvmdagent_deploy.properties in the same folder. To learn how to specify the input details in a properties file, view the sample properties file sample_jvmdagent_deploy.properties.

Upgrading ADP Agents Manually Using deploy_adpagent.pl

You can upgrade ADP Agents manually, using the deploy_adpagent.pl script. You can run this script only in silent mode, that is, you must specify all the input details using a properties file.

To upgrade ADP Agents manually using deploy_adpagent.pl, follow these steps:

1. Navigate to the following location on the OMS host:

   $<MIDDLEWARE_HOME>/plugins/oracle.sysman.emas.oms.plugin_12.1.0.4.0/archives/jvmd/deploymentScripts/agent/adp/

2. View the README.txt file, for information on using the deploy_adpagent.pl script.

3. Specify all the inputs in a properties file, then use the following command:

   perl deploy_adpagent.pl <properties_file_name>

   If you do not pass the name of the properties file as a parameter while running deploy_adpagent.pl, deploy_adpagent.pl looks for a properties file named adpagent.properties in the same folder. To learn how to specify the input details in a properties file, view the sample properties file SAMPLE_adpagent.properties.